ENH: usecols takes input order for read_csv implementation review #61967
+66
−1
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… complicated usecols order
eicchen
changed the title
| False, | ||
| ": bool\n " | ||
| "Whether usecols parameter will use order of input when " | ||
| "making a DataFrame. \n This feature will be default in pandas 3.0" |
There was a problem hiding this comment.
i think if this option is being introduced in 3.0 it won't be enforced until 4.0
There was a problem hiding this comment.
Sounds good, is that the only concern with the implementation? If so I'll go ahead and apply it to other functions and update the docs.
I can also add modifying the flag to 4.0 milestones too, idk if there is a timeline for it just yet but figured better to add it while it's fresh
There was a problem hiding this comment.
i think we said this should default to "warn"?
There was a problem hiding this comment.
Yeah, have it pop up and warn users that this was going to be a future change coming in 4.0. Unless you're talking about something else?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
doc/source/whatsnew/vX.X.X.rstfile if fixing a bug or adding a new feature.This is just the implementation for using usecols order for read_csv that I wanted to have people look at before moving to apply it to other places like read_excel and read_clipboard. If it all looks good, I'll go back and add all necessary documentation about future deprecation along with a popup when using usecols. This is mainly just for checking that the implementation doesn't have any glaring issues.
I ran the entire test suite just to be safe and it all looks good. The only thing the errored were some datetime tests that had nothing to do with the changes that I could find.
Oh it is also worth noting that pyarrow already uses the usecols order by default so that's probably worth adding to the documentation regardless